home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20041116-20060924
/
000130_fdc@columbia.edu_Tue Jul 19 16:43:09 2005.msg
< prev
next >
Wrap
Internet Message Format
|
2006-09-27
|
4KB
Path: newsmaster.cc.columbia.edu!not-for-mail
From: Frank da Cruz <fdc@columbia.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: tool to interpret packets? and Qs about lineout!
Date: 19 Jul 2005 20:42:27 GMT
Organization: Columbia University
Lines: 80
Message-ID: <slrnddqpdj.jfk.fdc@sesame.cc.columbia.edu>
References: <MpVBe.2319$Q75.431306@newshog.newsread.com> <H7WBe.1111$Na6.495200@twister.nyc.rr.com> <shdDe.2797$S17.567215@monger.newsread.com>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: sesame.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1121805747 29939 128.59.59.56 (19 Jul 2005 20:42:27 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 19 Jul 2005 20:42:27 GMT
User-Agent: slrn/0.9.8.0 (SunOS)
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15372
On 2005-07-19, Mark <sober@localbar.com> wrote:
: "Jeffrey Altman" <jaltman2@nyc.rr.com> wrote in message
: news:H7WBe.1111$Na6.495200@twister.nyc.rr.com...
:>> Are there any utilities available (for FreeBSD or dos/windows) which can
:>> be fed raw packet data and interpret the commands that were issued?
:>> What I'd like to see is the command issued to generate a packet such as:
:>> [soh]0 Iz @-Y1~@ 5T7[cr]
:>> (and many, many others)
:
You should be able to find a copy of the original Kermit book:
http://www.columbia.edu/kermit/manuals.html#ktb
(which went out of print a couple years ago) in a library. It contains
a specification of the protocol and packet formats. There have been some
changes since then, but nothing to invalidate what's in the book, at least
not as far as packet format and types are concerned.
I'm not sure what you mean by "commands". If a command such as "send *.zip"
was given, it could result in hundreds, thousands, or millions of packets,
of various types.
: I will be using c-kermit for a client but the commands I'm currently
: trying to interpret are embedded in utilities which establish a
: serial connection to a closed system (for purpose of data retrieval).
: Unfortunately, the source is not available and the utilities run on
: the wrong OS... therefore I currently have to run the utilities on 1 OS
: to retrieve data, but then transfer data to another server for processing.
: I'd like to use c-kermit on the processing machine to script the entire
: process so that it may be automated and bypass the need for the
: utilities completely.
:
You should be able to do that.
: With a data-scope I'm able to see the packets going back and forth,
: which is why I asked a second question about the lineout command
: (unaswered question follows):
:>> If I were to use the 'lineout' command to output my own 'packet' (i.e.,
:>> header/length/seq/type/data/cksum) would it be interpretted
:>> properly on the other side and be handled accordingly? (assume a properly
:>> formatted packet with a valid command type and data segment)
:
Yes, it is possible to implement the Kermit protocol itself in a Kermit
script, but I'm not aware of anyone actually having done it. You can see a
trivial example (not the whole protocol, but the use of INPUT and OUTPUT
commands to receive and send a few packets) here:
http://www.columbia.edu/kermit/ckscripts.html#protocol
And something similar, a complete implementation of TAP, the alpha pager
protocol which uses packets similar to Kermit's, here:
http://www.columbia.edu/kermit/ckscripts.html#page
: If the answer to that question is yes, the next question is:
: how can the lineout command be used to transfer (packet data) commands
: from a disk file?
:
Use FOPEN to open the disk file, FREAD to read data from it into variables,
use LINEOUT to send the contents of the variables. Brief example:
fopen /read \%c foo.bar
if fail blah blah
...
fread \%c line
if fail blah blah
lineout \m(line)
...
fclose \%c
But if this is Kermit protocol then you can't just send the data bare, you
have to encapsulate it in a packet and "encode" it according to the
negotiated options. Ditto for incoming data.
I don't understand enough about your setup to comment further. But if the
black box is executing Kermit protocol in a standard enough way that you
can communicate with it with C-Kermit, then the task might be simpler than
it appears at the moment.
- Frank